Skip to content

BUG: read_parquet from public parquet file with AWS credentials in environment gives OSError #54878

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

SanjithChockan
Copy link
Contributor

@SanjithChockan SanjithChockan commented Aug 30, 2023

Added retry mechanism so public parquet files from s3 can be read regardless of valid or invalid credentials.

@SanjithChockan SanjithChockan changed the title added retry mechanism to read_parquet with pyarrow BUG: read_parquet from public parquet file with AWS credentials in environment gives OSError Aug 30, 2023
Copy link
Member

@mroeschke mroeschke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the idea is to reuse _get_filepath_or_buffer if possible

@SanjithChockan
Copy link
Contributor Author

I think the idea is to reuse _get_filepath_or_buffer if possible

I don't think it's possible to use _get_filepath_or_buffer because pyarrow doesn't support storage_options. If there is a work around to reuse _get_filepath_or_buffer, it would no longer be using the pyarrow FileSystem then and would default to fsspec.

@mroeschke
Copy link
Member

It would be good to unify the two since they perform very similar things

@mroeschke
Copy link
Member

Thanks for the pull request, but it appears to have gone stale. If interested in continuing, please merge in the main branch, address any review comments and/or failing tests, and we can reopen.

@mroeschke mroeschke closed this Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: read_parquet from public parquet file with AWS credentials in environment gives OSError
2 participants